Testing Report (Spirits)

Revision History:

Introduction

Intended Audience and Purpose

This document provides the testing method and results, corresponding to the requirement from the customer. It consists of 3 parts, the testing cases, the test plan, and the testing results.

How to use the document

You may refer to the content section for the structure of the document, in which Sec. Testing Cases collect the unit and module test information from each team; Sec. Testing Plan shows the steps and expected results of the integration test; Sec. Results describes the real world data out of the test, and the correspondence to the requirements.

Test Case

Spirits

All test case below require a stable network connection in general

GUI

1. Webpage Openability
   (1) Prerequisite
   None
   (2) Test Steps
   a. Open (every) webpage [ckpt 1]
   (3) Expected Result
   a. The webpage can be opened in 1s[ckpt 1]
2. Dimension Adaptability
   (1) Prerequisite
   None
   (2) Test Steps
   a. Open (every) webpage [ckpt 1]
   b. Resize the browser[ckpt 2]
   (3) Expected Result
   a. The webpage is opened in 1s[ckpt 1]
   b. The layout of the webpage adjust rationally to make the webpage looks normal under different dimension. [ckpt 2 ]
3. Buttons&Hyperlinks Work as Expected
   (1) Prerequisite
   None
   (2) Test Steps
   a. Open webpage [ckpt 1]
   b. Click buttons&hyperlinks[ckpt 2]
   (3) Expected Result
   a. The webpage is opened in 1s[ckpt 1]
   b. Buttons and hyperlinks work as expected, i.e. buttons work normally/link to correct subpages[ckpt 2]

Admin Privileges

3. Admin log in—Normal
   (1) Prerequisite
   None
   (2) Test Steps
   a. Open related webpage [ckpt 1]
   b. Input login info [ckpt 2]
   c. Login [ckpt 3]
   (3) Expected Result
   a. The webpage is opened in 1s normally [ckpt 1]
   b. The login info can be input normally [ckpt 2]
   c. The webpage redirect(200 succ.) or prompt wrong/mismatched usrname&passwd according to server response(403/Timeout: failed) [ckpt 3]
4. Admin log in—Empty UserName
   (1) Prerequisite
   None
   (2) Test Steps
   a. Open related webpage [ckpt 1]
   b. Input password but leaves username to be empty[ckpt 2]
   c. Try to log in
   (3) Expected Result
   a. The webpage is opened in 1s normally [ckpt 1]
   b. The login info can be input normally [ckpt 2]
   c. The login button is locked since empty username is not permitted, and prompt info is shown [ckpt 3]
5. Admin log in—Empty Password
   (1) Prerequisite
   None
   (2) Test Steps
   a. Open related webpage [ckpt 1]
   b. Input username but leave password to be empty[ckpt 2]
   c. Try to log in
   (3) Expected Result
   a. The webpage is opened in 1s normally [ckpt 1]
   b. The login info can be input normally [ckpt 2]
   c. The login button is locked since empty password is not permitted, and prompt info is shown [ckpt 3]
6. Admin log out
   (1) Prerequisite
   None
   (2) Test Steps
   a. Open related webpage [ckpt 1]
   b. Logout [ckpt 2]
   (3) Expected Result
   a. The webpage is opened in 1s normally [ckpt 1]
   b. The webpage redirect and prompt logout succeful(200 succ.) or do nothing(Timeout: failed) [ckpt 2]
7. Admin downloads the calibration data from the cloud—Normal
   (1) Prerequisite
   a. The admin is logged in
   (2) Test Steps
   a. Open related webpage [ckpt 1]
   b. Input device uuid [ckpt 2]
   c. Download calibration data [ckpt 3]
   d. Check if the calibration data is downloaded successfully [ckpt 4]
   (3) Expected Result
   a. The webpage is opened in 1s normally [ckpt 1]
   b. The uuid can be input normally, and uuid format is checked, if is invalid then download button is locked [ckpt 2]
   c. The webpage prompts the user download starts [ckpt 3]
   d. The calibration data is downloaded. [ckpt 4]
8. Admin downloads the calibration data from the cloud—Exception(no calibration data(404), server respond timeout, network broke halfway, e.t.c.)
   (1) Prerequisite
   a. The admin is logged in
   (2) Test Steps
   a. Open related webpage [ckpt 1]
   b. Input device uuid [ckpt 2]
   c. Download calibration data [ckpt 3]
   (3) Expected Result
   a. The webpage is opened in 1s normally [ckpt 1]
   b. The uuid can be input normally, and uuid format is checked, if it’s invalid then download button is locked [ckpt 2]
   b. The webpage prompts user error according to server response[ckpt 3]
9. Admin uploads a new model to the cloud—Normal
   (1) Prerequisite
   a. The admin is logged in
   (2) Test Steps
   a. Open related webpage [ckpt 1]
   b. Input device uuid [ckpt 2]
   c. Upload calibration data [ckpt 3]
   (3) Expected Result
   a. The webpage is opened in 1s normally [ckpt 1]
   b. The uuid can be input normally, and uuid format is checked, if it’s invalid then upload button is locked [ckpt 2]
   c. The webpage prompts the user upload starts [ckpt 3]
10. Admin uploads a new model to the cloud—Exception(server respond timeout, network broke halfway, e.t.c.)
    (1) Prerequisite
    a. The admin is logged in
    (2) Test Steps
    a. Open related webpage [ckpt 1]
    b. Input device uuid [ckpt 2]
    c. Upload calibration data [ckpt 3]
    (3) Expected Result
    a. The webpage is opened in 1s normally [ckpt 1]
    b. The uuid can be input normally, and uuid format is checked, if it’s invalid then upload button is locked [ckpt 2]
    c. The webpage prompts the user error [ckpt 3]
11. Admin clear/ban a device
    (1) Prerequisite
    a. The admin is logged in
    (2) Test Steps
    a. Open related webpage [ckpt 1]
    b. Input device uuid [ckpt 2]
    c. Click ban/clear button [ckpt 3]
    (3) Expected Result
    a. The webpage is opened in 1s normally [ckpt 1]
    b. The uuid can be input normally, and uuid format is checked, if it’s invalid then upload button is locked [ckpt 2]
    c. The webpage prompts the user operation status (200 succ, no resp. failed).[ckpt 3]
12. Admin upload&set base model—Normal
    (1) Prerequisite
    a. The admin is logged in
    (2) Test Steps
    a. Open related webpage [ckpt 1]
    b. Selete and upload model [ckpt 2]
    (3) Expected Result
    a. The webpage is opened in 1s normally [ckpt 1]
    b. Model can be seletd and is uploaded to server. The webpage prompts successful operation(200:succ.) [ckpt 2]
13. Admin upload&set base model—Exception(server respond timeout, network broke halfway, e.t.c.)
    (1) Prerequisite
    a. The admin is logged in
    (2) Test Steps
    a. Open related webpage [ckpt 1]
    b. Select and upload a model [ckpt 2]
    (3) Expected Result
    a. The webpage is opened in 1s normally [ckpt 1]
    b. Model can be seletd and is uploaded to server. The webpage prompts error. [ckpt 2]

User Cloud Operation

1. User sets the contact email—Correct email
   (1) Prerequisite
   a. The device is connected and activated already
   (2) Test Steps
   a. Open related webpage [ckpt 1]
   b. Inputs email of correct format [ckpt 2]
   c. Submit [ckpt 3]
   d. Check if email is set successfully [ckpt 4]
   (3) Expected Result
   a. The webpage is opened in 1s normally [ckpt 1]
   b. The email can be input normally [ckpt 2]
   c. The submit button can be clicked normally [ckpt 3]
   d. The webpage prompts the user success [ckpt 4]
   (4) Sample Test Data
   a. sample123@qq.com
   b. sample55@163.com
   c. sample@jlu.edu.cn
   d. sample@sample.net
2. User sets the contact email—Email of wrong format
   (1) Prerequisite
   a. The device is connected and activated already
   (1) Test Steps
   a. Open related webpage [ckpt 1]
   b. Inputs email of wrong format [ckpt 2]
   (2) Expected Result
   a. The webpage opens in 1s normaly [ckpt 1]
   b. The email can be input normally, but the webpage prompts the user wrong email format and locks the submit button [ckpt 2]
   (3) Sample Test Data
   a. sdfsadf
   b. -+23.-0512
   c. www.baidu.com
   d. @@@@@
3. User sets the contact email—Too long email
   (1) Prerequisite
   a. The device is connected and activated already
   (1) Test Steps
   a. Open related webpage [ckpt 1]
   b. Inputs extremely long email(length>254) [ckpt 2]
   (2) Expected Result
   a. The webpage is opened in 1s normally [ckpt 1]
   b. Only the first 254 characters can be inputed. [ckpt 2]
   (3) Sample Test Data
   a. c…c(c*255)
4. User sets the contact email—Other exception(Server returns 400)
   (1) Prerequisite
   a. The device is connected and activated already
   (1) Test Steps
   a. Open related webpage [ckpt 1]
   b. Inputs email of correct format [ckpt 2]
   c. Submit [ckpt 3]
   d. Check set status [ckpt4]
   (2) Expected Result
   a. The webpage is opened in 1s normally [ckpt 1]
   b. The email can be input normally [ckpt 2]
   c. The submit button can be clicked normally[ckpt 3]
   d. The webpage prompts the user setting failure. [ckpt4]
   (3) Sample Test Data
   a. sample123@qq.com
   b. sample55@163.com
   c. sample@jlu.edu.cn
   d. sample@sample.net
5. User inspects the contact email—Email was set already
   (1) Prerequisite
   a. The device is connected and activated already
   (1) Test Steps
   a. Open related webpage [ckpt 1]
   (2) Expected Result
   a. The webpage is opened in 1s normally and shows the set email [ckpt 1]
6. User inspects the contact email—Email was not set yet
   (1) Prerequisite
   a. The device is connected and activated already
   (1) Test Steps
   a. Open related webpage [ckpt 1]
   (2) Expected Result
   a. The webpage is opened in 1s normally but prompts user unset email [ckpt 1]
7. User deletes email setting—Email was set already
   (1) Prerequisite
   a. The device is connected and activated already
   (1) Test Steps
   a. Open related webpage [ckpt 1]
   b. Deletes email setting [ckpt 2]
   (2) Expected Result
   a. The webpage is opened in 1s normally [ckpt 1]
   b. The email setting is deleted successfully and the webpage prompts user successful operation. [ckpt 2]
8. User deletes email setting—Email was not set yet
   (1) Prerequisite
   a. The device is connected and activated already
   (1) Test Steps
   a. Open related webpage [ckpt 1]
   (2) Expected Result
   a. The webpage is opened in 1s normally but the ‘delete’ button is locked [ckpt 1]
9. User checks calibration data availability on the server
   (1) Prerequisite
   a. The device is connected and activated already
   (2) Test Steps
   a. Open related webpage [ckpt 1]
   (3) Expected Result
   a. The webpage is opened in 1s normally and shows if the calibration data is available on server currently according to server response(404 no, 200 yes) [ckpt 1]
10. User uploads new calibration data to the cloud —Normal
    (1) Prerequisite
    a. The device is connected and activated already
    (2) Test Steps
    a. Open related webpage [ckpt 1]
    b. Upload data [ckpt 2]
    (3) Expected Result
    a. The webpage is opened in 1s normally [ckpt 1]
    b. The webpage prompts user successful operation[ckpt 2]
11. User uploads new calibration data to the cloud—Exception(invalid signature, no calibration data, server respond timeout, network broke halfway, e.t.c.)
    (1) Prerequisite
    a. The device is connected and activated already
    (2) Test Steps
    a. Open related webpage [ckpt 1]
    b. Upload the data [ckpt 2]
    (3) Expected Result
    a. The webpage is opened in 1s normally [ckpt 1]
    b. The webpage prompts the user error according to server response(400(cloud side): invalid signature, 404(device side):no calibration data, Timeout: upload failed)[ckpt 2]
12. User clears calibration data from the cloud
    (1) Prerequisite
    a. The device is connected and activated already
    (1) Test Steps
    a. Open related webpage [ckpt 1]
    b. Clears the email setting [ckpt 2]
    (2) Expected Result
    a. The webpage is opened in 1s normally [ckpt 1]
    b. The calibration data is deleted successfully and the webpage prompts user successful operation. [ckpt 2]
13. User checks the version of the device model on the server
    (1) Prerequisite
    a. The device is connected and activated already
    (2) Test Steps
    a. Open related webpage and check the version [ckpt 1]
    b.
    (3) Expected Result
    a. The webpage is opened in 1s normally and shows the current model version according to server response.[ckpt 1]
14. User downloads the newest model from server—Normal
    (1) Prerequisite
    a. The device is connected and activated already
    (2) Test Steps
    a. Open related webpage [ckpt 1]
    b. Downloads the model [ckpt 2]
    c. Check if the model is downloaded successfully [ckpt 3]
    (3) Expected Result
    a. The webpage is opened in 1s normally [ckpt 1]
    b. The webpage prompts user download starts.[ckpt 2]
    c. The model is downloaded successfully [ckpt 3]
15. User downloads the newest model from server—Exception(server respond timeout, network broke halfway, e.t.c.)
    (1) Prerequisite
    a. The device is connected and activated already
    (2) Test Steps
    a. Open related webpage [ckpt 1]
    b. Downloads the model [ckpt 2]
    (3) Expected Result
    a. The webpage is opened in 1s normally [ckpt 1]
    b. The webpage prompts the user error.[ckpt 2]
16. User resets model version—Normal
    (1) Prerequisite
    a. The device is connected and activated already
    (2) Test Steps
    a. Open related webpage [ckpt 1]
    b. Resets the model [ckpt 2]
    (3) Expected Result
    a. The webpage is opened in 1s normally [ckpt 1]
    b. The webpage prompts user reset succeeded [ckpt 2]
17. User resets model version—Exception(server respond timeout, network broke halfway, e.t.c.)
    (1) Prerequisite
    a. The device is connected and activated already
    (2) Test Steps
    a. Open related webpage [ckpt 1]
    b. Resets the model [ckpt 2]
    (3) Expected Result
    a. The webpage is opened in 1s normally [ckpt 1]
    b. The webpage prompts the user error.[ckpt 2]

User Local Operation

27. User connects the device
    (1) Prerequisite
    None
    (2) Test Steps
    a. Open related webpage [ckpt 1]
    b. Selects and connects a device [ckpt 2]
    (3) Expected Result
    a. The webpage is opened in 1s normally [ckpt 1]
    b. The webpage prompts user connecting result(200:succ, timeout:failed) [ckpt 2]
28. User gets and inspects status information of the device
    (1) Prerequisite
    a. The device is connected and activated
    (2) Test Steps
    a. Open related webpage [ckpt 1]
    b. Gets status information [ckpt 2]
    (3) Expected Result
    a. The webpage is opened in 1s normally [ckpt 1]
    b. The webpage shows the information gotten [ckpt 2]
29. User download the model from the device—Normal
    (1) Prerequisite
    a. The device is connected and activated
    (2) Test Steps
    a. Open related webpage [ckpt 1]
    b. Downloads the model from the device [ckpt 2]
    c. Check if the model is downloaded successfully [ckpt 3]
    (3) Expected Result
    a. The webpage is opened in 1s normally [ckpt 1]
    b. The webpage shows download starts [ckpt 2]
    c. The model is downloaded successfully [ckpt 3]
30. User download the model from the device—Excetion(No model currently(404), server respond timeout, e.t.c.)
    (1) Prerequisite
    a. The device is connected and activated
    (2) Test Steps
    a. Open related webpage [ckpt 1]
    b. Downloads the model from the device [ckpt 2]
    (3) Expected Result
    a. The webpage is opened in 1s normally [ckpt 1]
    b. The webpage prompts error(404:no model, Timeout:operation failed) [ckpt 2]
31. User starts to calibrate
    (1) Prerequisite
    a. The device is connected and activated
    (2) Test Steps
    a. Open related webpage [ckpt 1]
    b. Starts to calibrate [ckpt 2]
    c. Finish calibrate [ckpt 3]
    (3) Expected result
    a. The webpage is opened in 1s normally [ckpt 1]
    b. The webpage shows calibration guide according to server response [ckpt 2]
    c. The webpage prompts users calibrating finished [ckpt 3]
32. User deletes local calibration data
    (1) Prerequisite
    a. The device is connected and activated
    (2) Test Steps
    a. Open related webpage [ckpt 1]
    b. Clears local calibration data. [ckpt 2]
    (3) Expected result
    a. The webpage is opened in 1s normally [ckpt 1]
    b. The webpage prompt user operation status according to server response(200:succ, timeout:failed) [ckpt 2]

Test Plan

Introduction

Purpose

The test plan introduces how to test the interaction module of the system, which provides testing range, testing strategy and personnel arrangement, e.t.c.

Background

The interaction module is responsible for the interaction with users, the display of information, and system management by administrator.

Features to Be Tested

Features below are planned to be tested to ensure the interaction module of the system meets the specified requirements

1. Administrator Privileges

• Login and Logout
• Model Management
   Upload new model
   Set base model
   Reset model
• Device Management
   Clear data coresponding to a specified device
   Ban a device
   Download calibration data of a specified device

3. User Cloud Operation

• User Identification
   Set email
   Inspect current email setting
   Delete current email setting
• Calibration-related
   Update new calibration data
   Check calibration data availability on the cloud
   Clear calibration data on the cloud
• Model-related
   Check current model version
   Download the newest model from cloud
   Reset model version

4. User Device Operation

• Connectivity
   Connect to the device
• Calibration-related
   Start to calibrate
   Clear local calibration data
• Data Exchange
    Get device status information
    Download the model from the device
    Upload a new model to the device

5. GUI

• User-friendly
   Good appearance
   Rational layout design
   Clear button/link/… naming
   Acceptable response time
• Compatibility
   Resposive Design
   Cross-platform

6. Error Handling

Factors not considered currently

  In current stage, we assume there is a relatively stable network connection while using the system. Therefore, network failure is ignored.
  Besides, we do not consider safety issues

…

Test Reference and Submission Documentation

Test Reference Documentation

1. System Requirement Specification
2. System Design Specification
3. Interface Specification

Test Submission Documentation

1. Test Plan
2. Test Case
3. Test Report
4. Current Bugs

Test Timeline

Test Resource

Personnel

Weibin CHENG

Environment

Windows 11
Google Chrome Version 100.0.4896.127 (Official Build) (64-bit)
…(e.t.c)

Test Results(Based on Requirement Analysis)

End User

Connect App to Device

See Device Status

Calibrate Device

Choose Algorithm to train

Set Contact Email

Download Model for Chosen Algorithm

Clear(Part of) Data from Cloud

Reset Device

Power Off Device

Enterprise

Set up Cloud & Produce Device

Login

Download Calibration Data of Device from Cloud

Download Model from Device

Upload Model for Device on Cloud

Upload Base Model for Algorithms on Cloud

Delete Cloud Model